that looks cool

that looks cool

It looks cool on the flat screen right now, but it's not so great when you try it. You'd probably get motion sickness. I'm still working on it.

sadly i dont think that's possible to stop this.

Does this show the same scratch 3D perspective to both eyes?

Does this show the same scratch 3D perspective to both eyes?

A-frame has stereoscopic rendering built in and I've enabled it in the rendering settings, so no. This fixes some issues with visualizing depth, so the eye offset allows your brain to process the image with more clarity. Even if the matrices aren't used in the renderer, it should properly use the correct eye offset. Why do you ask, just out of curiosity? If you'd like I could add a block that disables or enables this feature, in case the Scratcher wants to build that framework themselves, which I'd doubt.

Keep in mind this is still a work in progress and most of the code is many months old so it's not the most efficient way to do VR.

Why do you ask, just out of curiosity?

Yes. At one point I tried to extend my AR extension to support AR headsets and VR as well, but the multiple eye rendering has been the main thing holding me back. I was just curious to know how you solved it.

Why do you ask, just out of curiosity?

Yes. At one point I tried to extend my AR extension to support AR headsets and VR as well, but the multiple eye rendering has been the main thing holding me back. I was just curious to know how you solved it.

I believe that there can be two XRViewerPose matrices for each eye if available, according to Mozilla Docs. You might want to look into that again. It'd be great if Augmented Reality could support AR headsets such as the Oculus Quest 3 in addition to just mobile touchscreen devices. There should be a views array that can do this. An example can be seen here. Just a suggestion though. I simply think having AR headsets would be a nice update.

I'll take a look when I have time. Thought it will probably be hard because the only kind of VR I have access to is phone-based 3DOF no controller VR.

Also, do you mind giving some links, so that I can faster figure out where to look?

I'll take a look when I have time. Thought it will probably be hard because the only kinf of VR I have access to is phone-based 3DOF no controller VR.

Also, do you mind giving some links, so that I can faster figure out where to look?

As for VR testing, you wouldn't really need a VR headset. I've used Meta Quest's Immersive Web Emulator extension for testing when I didn't care to load up the entire headset.

ah yes, I remember seeing a trailer for this on scratch. I wanted to help, but now I can't

nvm I think I can
i'm Martinelplayz on scratch btw

could i try the extension?

Hi siskka7 it's me Thebloxers998

Thebloxers998

hmm https://github.com/TurboWarp/extensions/blob/2837a7adfbfc2e3aba49108003686affa1cb7beb/extensions/MasterMath/BlockifyVR.js

Thebloxers998

hmm https://github.com/TurboWarp/extensions/blob/2837a7adfbfc2e3aba49108003686affa1cb7beb/extensions/MasterMath/BlockifyVR.js

I'm not sure what you're "hmm"ing. It's just the source code.

Hi, nice extension

I'll take a look when I have time.

I took a look and have no idea. It's all code specific to AFRAME. I don't know AFRAME. AFRAME is too big and complicated for me to try to debug, especially if the only tool in my disposal is WebXR API Emulator browser extension.

Nic3

Nice*

4. R.js" to download JUST THE EXTENSION. Do NOT download the entire .zip source code of the whole repositor

thank for your very fast response

"Ready for review" Yay

it works now .i found on quest 3 that there is down black stripe like it looks like it was flat screen folowing me (no rotation lag) but screen ends down

i found that when blocks dont work on quest 3 (not big problem for me beceause i can live withow it + we have if blocks)

i found that when blocks dont work on quest 3 (not big problem for me beceause i can live withow it + we have if blocks)

Could you please specify which blocks weren't working on Quest 3? I'm assuming you're referring to the "When" hat blocks, such as "when key pressed" or "when controller connected".

Please note that most blocks will return nothing at all unless you're in a VR session (e.g., pressing the block to reveal its value in the editor doesn't work). They must be used properly and will only return their proper values after the enter vr mode block has finished executing. The same rules go for the "when" hat blocks.

This is why I needed to provide a sample project, as I haven't made the blocks return any in-editor fallbacks yet.

By my testing, all blocks currently work on quest 2 except the get matrix block.

Oh i inspected only when (key/button) pressed and i was in vr mode not in editor

3.0 big update idea body tracking (this is just idea. i am pretty sure that this will be hard to code)
Edit: probably not useful

()-rotation of headset
and
()-position of headset
i cant click/switch to any controlers when i open menu there is check icon behind all options (i am on pc and it may be a bug that everything is selected. i did not learned javascript but the check is everywhere but in default blocks there is only one check. the selected one)

3.0 big update idea body tracking (this is just idea. i am pretty sure that this will be hard to code) Edit: probably not useful

Not supported by A-frame (or WebXR as far as I'm aware of)

probably nobody using the extension has a full-body tracking suit and Oculus standalone full-body tracking isn't consistent.

()-rotation of headset
and
()-position of headset
i cant click/switch to any controlers when i open menu there is check icon behind all options (i am on pc and it may be a bug that everything is selected. i did not learned javascript but the check is everywhere but in default blocks there is only one check. the selected one)

No idea what this is about. I haven't really tested on PC VR as my main focus is standalone. The blocks seem to work fine for me and I've never seen multiple menu options selected in a scratch block.

Sometimes pressing menu inputs in the oculus browser with the oculus controllers is a little tricky

i did not mean pc vr but when i was coding this bug showed up (i use github to share projects)

here is my test project that logs vr input https://github.com/siskka7/siskka7/blob/main/vr%20blockify%20input%20logger.sb3
(tutorial in project) note that this is before was "when block" was fixed i hope this will help developing

3.0 big update idea body tracking (this is just idea. i am pretty sure that this will be hard to code) Edit: probably not useful

Not supported by A-frame (or WebXR as far as I'm aware of)

https://github.com/immersive-web/body-tracking

3.0 big update idea body tracking (this is just idea. i am pretty sure that this will be hard to code) Edit: probably not useful

Not supported by A-frame (or WebXR as far as I'm aware of)
probably nobody using the extension has a full-body tracking suit and Oculus standalone full-body tracking isn't consistent.

()-rotation of headset
and
()-position of headset
i cant click/switch to any controlers when i open menu there is check icon behind all options (i am on pc and it may be a bug that everything is selected. i did not learned javascript but the check is everywhere but in default blocks there is only one check. the selected one)

No idea what this is about. I haven't really tested on PC VR as my main focus is standalone. The blocks seem to work fine for me and I've never seen multiple menu options selected in a scratch block.
Sometimes pressing menu inputs in the oculus browser with the oculus controllers is a little tricky

i did not mean pc vr but when i was coding this bug showed up (i use github to share projects)

I believe that the "When button pressed" block issue you're describing is due to a recent change where I made the block inputs allow reporters, but I don't think hat blocks like inputs that allow reporters. I'll get another release out soon that should fix this issue. I'm not sure what you mean by the other blocks though, everything else seems to work fine except the get matrix block

i think there is big misunderstanding i dont thought hat block but (picture1)

and the menu looks like (picture2)

3.0 big update idea body tracking (this is just idea. i am pretty sure that this will be hard to code) Edit: probably not useful

Not supported by A-frame (or WebXR as far as I'm aware of)
probably nobody using the extension has a full-body tracking suit and Oculus standalone full-body tracking isn't consistent.

()-rotation of headset
and
()-position of headset
i cant click/switch to any controlers when i open menu there is check icon behind all options (i am on pc and it may be a bug that everything is selected. i did not learned javascript but the check is everywhere but in default blocks there is only one check. the selected one)

No idea what this is about. I haven't really tested on PC VR as my main focus is standalone. The blocks seem to work fine for me and I've never seen multiple menu options selected in a scratch block.
Sometimes pressing menu inputs in the oculus browser with the oculus controllers is a little tricky

i did not mean pc vr but when i was coding this bug showed up (i use github to share projects)

I believe that the "When button pressed" block issue you're describing is due to a recent change where I made the block inputs allow reporters, but I don't think hat blocks like inputs that allow reporters. I'll get another release out soon that should fix this issue. I'm not sure what you mean by the other blocks though, everything else seems to work fine except the get matrix block

i think there is big misunderstanding i dont thought hat block but (picture1) and the menu looks like (picture2)

intriguing. Turbowarp menus aren't supposed to look like that, but I can guarantee it's probably not an extension issue.

so there is no fix idea :(

Don't know why the "when button" blocks still aren't working... sigh I guess I have another bug to fix cuz it was working earlier
Oh did not mean that

Don't know why the "when button" blocks still aren't working... sigh I guess I have another bug to fix cuz it was working earlier

Dang, but how did it end up bugging. Did you check the logic of the block

I guess this is ready for review now?

Yayyyyyyyy!!!!!!!

I guess this is ready for review now?

Yayyyyyyyy!!!!!!!

I Happy Now :)

So....

A-frame doesn't support detecting the menu button/pause button or the Oculus/system button on the oculus-touch-controls component. I tried detecting these manually through the Gamepad API but I guess they're not exposed or something because they don't work and I checked with ChatGPT and it said you couldn't get them.

I'm leaving the "menu" and "system" buttons in the menus of the blocks because they should still work on vive and windows mixed reality

Which speaking of I need people who can test non-Oculus platforms because I haven't really tested them at all.

Other than that I think this extension should be ready for release. I know a lot of them are busy but it'd be great if we could get some reviewers/moderators over here... this extension is moderately large so I expect it to take longer than normal to review

Ok

I think I'm going to make a few changes to make the code more "professional" and less messy but I can't right now so I'll get around to it when I'm less busy with other things

Likely includes using switch instead of if else in most of the block code and switching to a more object-oriented approach that's easier to work with and reducing the crazy variable situation

Still working on cleaning up some of the backend code...

• Use Scratch.Cast where necessary
• Use switch case instead of if else where more efficient
• Use a more object-oriented approach instead of a bajillion variables for easy getting/setting of values and reducing line count
• Some of this code is two years old and I didn't know what I was doing back then

Although these are easy and probably won't take forever, they're annoying and I'm putting them off for a while in favor of putting more time on a work-in-progress 3D physics extension